📣 Instructions

• Authors complete the Author's section. Use the italicized instructions to add detail to assist the reviewers.
• Create a DRAFT pull request.
• After completing the Author's Checklist, authors may update the PR to READY FOR REVIEW.
• Reviewers should complete the items in the Reviewer's Checklist before approving the pull request.

Change Summary

AUTHOR: Describe the changes included in this pull request. Link to the associated GitHub or Jira issue(s).

• Release 1.0.0

Author's Checklist

AUTHOR: Complete the following tasks before marking the PR as READY FOR REVIEW.

• Complete a self-review of changes
• Unit tests have been created or updated and all pass locally
• The code is free of [new] lint errors and warnings
• Documentation has been updated as needed: README, /docs, code comments, JSDoc, etc.
• All CI/CD checks pass

Testing Instructions

AUTHOR: Describe the process to verify and test the changes in this pull request. Include steps for both happy path and edge cases.

• [...Describe any setup required]

1. Full regression test.

Additional Information

AUTHOR: Optionally, provide additional details, screenshots, screen recordings, or URLs that may assist the reviewer.

• [Screenshot or recording of the change in action]
• [Link to related documentation or design]
• [Any known limitations or future considerations]
• [Dependencies or related PRs]

Reviewer's Checklist

REVIEWERS: Complete the following tasks before approving the PR.

Code Quality:

• Code changes are clear, maintainable, and follow project conventions
• Error handling and edge cases are appropriately covered
• All unit tests pass and test coverage is adequate
• Integration tests (if applicable) pass
• Code is free of [new] lint errors and warnings

Testing:

• The fix or feature works as intended per the story description and acceptance criteria
• Tests have been executed locally per the steps outlined below
• No regressions detected in related functionality

Security:

• No security vulnerabilities or hardcoded sensitive data introduced
• No external dependencies added without team discussion

Documentation:

• Documentation has been updated as needed: README, /docs, code comments, etc.